Skip to content
This repository was archived by the owner on Jan 13, 2026. It is now read-only.

Comments

feat: allow user to configure whether synonyms should or should not be included when determining exact matches#58

Merged
rkettelerij merged 2 commits intomasterfrom
exact-match-without-synonyms
Mar 19, 2025
Merged

feat: allow user to configure whether synonyms should or should not be included when determining exact matches#58
rkettelerij merged 2 commits intomasterfrom
exact-match-without-synonyms

Conversation

@rkettelerij
Copy link
Collaborator

@rkettelerij rkettelerij commented Mar 18, 2025

Description

Allow user to configure whether synonyms should or should not be included when determining exact matches

Type of change

  • Improvement of existing feature

Checklist:

  • I've double-checked the code in this PR myself
  • I've left the code better than before (boy scout rule)
  • The code is readable, comments are added that explain hard or non-obvious parts.
  • I've expanded/improved the (unit) tests, when applicable
  • I've run (unit) tests that prove my solution works
  • There's no sensitive information like credentials in my PR

@rkettelerij rkettelerij changed the title feat: allow user to configure weather synonyms should or should not be included when determining exact matches feat: allow user to configure whether synonyms should or should not be included when determining exact matches Mar 18, 2025
@rkettelerij rkettelerij force-pushed the exact-match-without-synonyms branch from 96cd29e to f94ca14 Compare March 18, 2025 15:24
…e included when determining exact matches - add test
@rkettelerij rkettelerij marked this pull request as ready for review March 19, 2025 10:00
@rkettelerij rkettelerij merged commit def1eb3 into master Mar 19, 2025
2 checks passed
@rkettelerij rkettelerij deleted the exact-match-without-synonyms branch March 19, 2025 20:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants